Part of #20171

This PR implements a new method in node-core:

registerModuleWrapper<OptionsType>({
  moduleName: 'express',
  supportedVersions: ['>=4<6'],
  options,
  patch: (moduleExports, getOptions) => {
    wrapExpressModule(moduleExports, getOptions);
  }
});

This works similarly to otel wrapping, registering the patch with IITM and RITM using the same semantics, more or less. It is a bit simplified for our requirements but should generally behave the same.

registerModuleWrapper is designed to be idempotent and to be callable multiple times. It will only actually patch once, calling it subsequently will update the options though - any options required in the patch should be resolved at runtime (!) via the passed-in getOptions. (Why, you may ask yourself? Because we rely on this for preloading OTEL instrumentation, where we run the patch in --import preload.ts or similar but do not have the options yet, which are defined later in init(), but should update the instrumentation config accordingly).

I have tentatively implemented this for the existing express instrumentation. This is def. a breaking change so nothing we can ship now but it should show how this can/should eventually look.

Note that this should not be merged as it is a breaking change and only for showcase & discussion how this can/should work.